There following defects are open in ExtremeCloud Orchestrator 3.6.0.
| Parent Defect ID: | XCO-8191 | Issue ID: | XCO-8191 |
|---|---|---|---|
| Product: | XCO – Fabric Skill | Reported in Release: | XCO 3.3.0 |
| Symptom: | If you run concurrent epg update commands operation as port-group-add or vrf-add on bridge-domain EPGs that are associated with more than one ctag, one or some of the commands can fail with the following error: Save for device failed. | ||
| Condition: | This is observed more often when more than 3 concurrent EPG port-group-add commands with non-conflicting ports and non-overlapping ctag-range are executed. Occasionally, configuration information that is pushed by one command is not used properly to prepare command recipe for another, causing the failure of one command. | ||
| Workaround: | Rerunning the failing command will succeed. The error is intermittent and does not cause permanent changes. XCO state information is not affected at any point. | ||
| Recovery: | No recovery is required as no state change is done as part of this failure. | ||
| Parent Defect ID: | XCO-9190 | Issue ID: | XCO-9190 |
|---|---|---|---|
| Product: | XCO - Common | Reported in Release: | XCO 3.3.0 |
| Symptom: | VM GUI Library matches shows 2 devices when only 1 device is discovered. | ||
| Condition: | Remove all the devices and discover only one device. | ||
| Workaround: | Discover device and remove all duplicate hash matches entries from match table for the device. | ||
| Recovery: | Remove all duplicate hash matches entries from match table for the device. | ||
| Parent Defect ID: | XCO-9307 | Issue ID: | XCO-9307 |
|---|---|---|---|
| Product: | XCO – Fabric Skill | Reported in Release: | XCO 3.4.0 |
| Symptom: | After the upgrade from 3.5.0 to 3.6.0, removing all the configuration from XCO/devices and restoring the 3.5.0 backup followed by manual DRC failed to push the configurations to the devices | ||
| Condition: | After the upgrade from 3.5.0 to 3.6.0 and when the user removes the configurations. Backup and restore work fine right after the upgrade without removing the configurations. | ||
| Workaround: | N/A | ||
| Recovery: | N/A | ||
| Parent Defect ID: | XCO-9363 | Issue ID: | XCO-9363 |
|---|---|---|---|
| Product: | XCO – Fabric Skill | Reported in Release: | XCO 3.4.0 |
| Symptom: | After removing the tenant using the --force option, Fabric binding is not applied on the physical interfaces which were part of the port-channel/physical interfaces. | ||
| Condition: | Issue is observed when user issues the command 'efa tenant delete --name <tenant_name> --force' | ||
| Workaround: | User needs to unbind the policies (QoS) from all the relevant targets (fabric/tenant/port/port channel/tenant endpoint group) before executing the force operations including delete to avoid the stale policies(QoS) in the system. | ||
| Parent Defect ID: | XCO-9769 | Issue ID: | XCO-9769 |
|---|---|---|---|
| Product: | XCO – Fabric Skill | Reported in Release: | XCO 3.4.1 |
| Symptom: | Unable to delete the prefix list from Policy Service , even though it is not binded in tenant service | ||
| Condition: | After deleting the ipv6 prefix from bgp-peer in tenant service, not able to delete prefix-list from policy service | ||
| Recovery: | Run the following CLI command: efa inventory device update --ip <> | ||
| Parent Defect ID: | XCO-9942 | Issue ID: | XCO-9942 |
|---|---|---|---|
| Product: | XCO – Fabric Skill | Reported in Release: | XCO 3.5.0 |
| Symptom: | Few PO's will remain on SLX Devices and few PO's will remain in XCO database after executing EPG delete and PO delete in quick succession (Two commands run at the same time). | ||
| Condition: | Few PO's will remain on SLX Devices and Few PO's will remain in XCO database after executing EPG delete and PO delete in quick succession (Two commands run at the same time). | ||
| Workaround: | Delete EPG and wait for the profile to be applied on the po's and then delete po's after making sure EPG delete is complete. | ||
| Recovery: | GO to SLX device and Remove the PO's manually and do inventory device update. | ||
| Parent Defect ID: | XCO-9983 | Issue ID: | XCO-9983 |
|---|---|---|---|
| Product: | XCO – Visibility Skill | Reported in Release: | XCO 3.5.0 |
| Symptom: | Faulty card state is shown as online. | ||
| Condition: | When the card type is changed to invalid type, card state will be shown as online or active though the card is in faulty state. | ||
| Workaround: | Set the correct card type based on the card present in device. | ||
| Recovery: | Delete and re-discover the device | ||
| Parent Defect ID: | XCO-10067 | Issue ID: | XCO-10067 |
|---|---|---|---|
| Product: | XCO – Fabric Skill | Reported in Release: | XCO 3.5.0 |
| Symptom: | After adding border-leaf to the fabric, fabric-internal profile is not getting applied on the MCT port-channel. | ||
| Condition: | After adding new devices(leaf/border-leaf) to the fabric followed by fabric configure, fabric-internal profile is not getting applied on the MCT Port-channel of the newly added devices(leaf/border-leaf). | ||
| Workaround: | User can issue rebind the fabric
internal port QoS profile using below command. Bind Fabric internal ports QoS profile: efa policy qos profile bind --name <profile_name> --fabric <fabric_name> --port fabric-internal |
||
| Recovery: | User can issue rebind the fabric
internal port QoS profile using below commands Bind Fabric internal ports QoS profile: efa policy qos profile bind --name <profile_name> --fabric <fabric_name> --port fabric-internal |
||
| Parent Defect ID: | XCO-10073 | Issue ID: | XCO-10073 |
|---|---|---|---|
| Product: | XCO – Visibility Skill | Reported in Release: | XCO 3.5.0 |
| Symptom: | Statistics are not displayed/updated in XCO device overview page | ||
| Condition: | When SLX (9140/9240) device is discovered with IPv6 address. | ||
| Workaround: | Discover the SLX device with IPv4 address. | ||
| Recovery: | Delete the device which is discovered with IPv6 address and re-discover with IPv4 address. | ||
| Parent Defect ID: | XCO-10430 | Issue ID: | XCO-10430 |
|---|---|---|---|
| Product: | XCO - Common | Reported in Release: | XCO 3.6.0 |
| Symptom: | In the firmware history page, the previous and target versions are interchanged during the firmware restore operation. The same issue is also seen in the firmware history CLI response. | ||
| Condition: | Firmware restore operation on a 9920 device or a fabric SLX device from the GUI or CLI. | ||